New Cloudflare Setting: Optionally fetch CF IPs on container boot. #2878
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With recent releases only local proxies are trusted by default. There is a setting that allows you to add IPs to this list but in cases where Cloudflare has a long list or often change IPs this can be troublesome.
This PR adds
PWP__CLOUDFLARE_PROXY=false
and acloudflare_proxy: false
in yoursettings.yml
. Set one of these totrue
to enable fetching of CloudFlare IPs on container boot.See #2799 for the discussion.
Related Issue
#2799
Type of Change
Checklist
rake test
)